Claude Code: How I Use It

How I currently use Claude Code. This is a living document that evolves with my workflow.

Environment

I use Ghostty for its simplicity, speed, and native macOS integration. I used to use tmux (see tmux + Neovim setup), but tmux adds another layer of latency and memory overhead. Now I just use Ghostty’s built-in splits: ⌘+D / ⌘+⇧+D.

My default layout is two panes side by side — Claude Code on the left, Neovim on the right. I split further as needed but try to return to this two-pane setup. Neovim is the right fit here for the same reason as Ghostty: snappy and versatile. You can quickly move around, explore files, and make edits while CC works in the other pane. I sometimes run watch scripts (e.g., auto-compile, file sync) in a tiny extra pane.

Usually I have several tabs open (one for each project) with each tab having 2+ panes.

CLAUDE.md setup

Three layers: - Global (~/.claude/CLAUDE.md): Python/uv preferences, wiki/blog paths, project tracking conventions, academic writing style - Project (CLAUDE.md): repo-specific instructions, commands, code style

Custom skills

I keep a small set of research-oriented skills. They include:

Plus the Anthropic document-skills plugin for PDF, PPTX, DOCX, etc.

Custom agents

My custom agents include:

Custom commands